home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 4
/
Aminet 4 - November 1994.iso
/
aminet
/
comm
/
fido
/
jm940928.lha
/
readme
< prev
Wrap
Text File
|
1994-09-28
|
36KB
|
1,152 lines
Those of you currently running a version of Jammail, please send me a message
with your current wish list and i'll see what I can do.
Note: Some users are still experiencing random crashes related to the
scheduler. Usually these are unaccellerated systems, but not always.
For systems having these symptoms, an old version of JamTool (0.28)
is also included in this archive which can be used.
Changes - September 18th -> 27th
- long drawn out battles with the emsi.library trying to get things
working with Shane connecting to D'Broke and one TrapDoor system.
- add line/modem option now setting default stack. Previously no default
was set, so 0 was used, which caused instant guru when new lines were
launched.
Changes - September 17th
- Login Menu Commands are now completely disablable - No Grabs, no downloadable
files and no bulletins. Very similar to a straight "FidoNet" frontend
mailer system.
Changes - September 16th
- Finishing off supporting alternative "node numbers" in the scheduler and
other areas.
Changes - September 15th
- Login Connect Msg can now be disabled (the connect / time line sent to
inbound callers)
- Each JamMail "node" can be considered a different "line" number relative
to the rest of your system. (ie, JamMail's first line could be line
number 4 of your BBS).
Changes - September 14th
- Little changes all over the system
- Default Cnet launch string now uses Cnet: assign.
- modem initializing sequence cleaned up
- Scheduler system numbers are now lined up correctly.
- Finally got someone online testing with both a bad Trapdoor system, and
a D'Broke system, so massssive amounts of outbound EMSI debugging done.
- thanks to Shane Gouseman from OHIO
- Outbound sessions to D'bridge seem to work perfectly now.
Changes - September 11th
- Bi-directional protocol display support added to WPL.
Bi-directional display version of XprZedZap created as well.
- *PLEASE* send me comments on the new xpr window look.
- Baud rated included in xpr transfer window title.
- jammail.library now correctly parses non-ftn addresses without
removing domain/sub-domain information for EMSI handshakes.
Changes - September 9th
- New and improved super duper (ya :-) outbound EMSI handling. I haven't
found a system it doesn't work on. There doesn't seem to be any timeout
problems anymore right at the start, so should fix problems connecting
to slow systems, or those with large banners.
- wording of "EMSI AKA's string" changed to "EMSI Addresses string", since
it does require your primary as well. These addresses are the *ONLY*
ones that will be sent in an EMSI session.
Changes - September 8th
- *FIXED* wplemsi.library stack usage that was causing "new" versions of
Jammail to crash after EMSI sessions.
- Added stack configuration option so each line can have its own stack
setting. 10k default, I would not suggest going lower than 5k or so.
Changes - September 6th
- fixed situation where outbound calls that collide with an inbound call
would be dialed again immediately, before inbound call is answered.
- removing transfer debugging (pi1, pi2,.... msg1,msg2)
Changes - September 2nd
- fixed getinbound command settings when EMSI is disabled completely
Changes - September 1st
- fixed bug in Modem response configs where it would allow more than 18
responses to be added.
Changes - August 30th
- added "q" and "x" as synonyms for the "quit" command at the login prompt.
- added "#? #?" as equivalent to typing ? which will catch people that type
in real/proper names at the prompt.
- possibly fixed problem with non-locked modems.
- added inbound EMSI_REQ banner at front of login stuff to possibly catch
some systems that can't handle banners before it.
Changes - somewhere in here
- JamScan 0.65 bug fixed regarding reading of #?.?LO files.
Was home for a weeks vacation. First time home since Easter!
Changes - August 17th
- Setup script now closes executing lines before starting up again
when scheduler isn't running, or the scheduler doesn't close them
down when the scheduler is closed.
- adding debugging during fidonet transfers trying to find location where
Xferq.library lockup occurs.
Changes - August 16th
- really fixed the ability to disable scheduler.
Changes - August 15th
- added "Reply ASAP" option to scheduler menu. This causes the line
to return a result of 0 for the call, as soon as it gets a connect
message. The "Real" call status is not returned. Those using the
JamMail scheduler that have multiple lines, can enable this to
allow multiple outbound calls at the same time. Previously, it
would only do one.
- return codes from "Call" commands directly to a line are now defined.
0 - session ok
1 - session failed (transfer)
5 - Busy
10 - Timeout/No Carrier (Maid Response)
15 - No Dial Tone (Line Response)
20 - Bad Site (no phone number)
25 - Bad Call type listed for site in phonebook (not supported)
30 - Failed Handshake.
- Added Ability to disable Scheduler again. Working towards cleaning
this area up.
- Call Collisions are now always forwarded directly back to the same
line to be done after inbound session is finished.
- updated todo list.
- updated makearchive script - now tests archive, and creates .readme
file.
Changes - August 12th
- Removed support for Ymodem transfer protocol. Nobody is ever going to
use it anyways.
- Playing a bit with supporting Dmodem protocol - Not working yet.
- Jamtool 0.28 included in archive. This is a downgrade, but does work
for everyone. This will be used the scheduler functions are finally
replaced. Because of this the "Adaptive" dialing will not work as
advertised.
Changes - August 10th
- Oops, I had included the debugging version of xferq.library. Sorry, back
to the regular one.
Changes - August 8th (or so)
- JamScan now able to handle tabs between columns.
- DUHHHH I didn't included "JamMail" itself in the last archive.
Changes - August 4th
- Massively changed outbound handshaking code in both JamMail and the
emsi.library.. Please let me know if you have any problems with
outbound EMSI sessions of any kind.
- if you do have a problem to report, please cut the debugging info
out of the modem window and send it to me.
- added variable $(connectmsg) which will contain the connect message
as it came in from the modem (ex. CONNECT 19200/ARQ/V42b)
Changes - July 29th
- screwed up memory allocations and such, had to go back to a version
a couple days old. hate it when that happens.
- improved answering code for slow/busy system situations, where the
system may not have caught the rings at the right time, and they call
came blasting in causing the system to answer multiple times, thus
cancelling the first answer and hanging up.
- debugging code added (just little msg displays in the modem window)
right after fido sessions during hangup and such trying to find
stray bug causing the system to hault after hanging up.
changes - July 27th
- another emsi.library - still trying to fix problems with calling
emsi systems with large banners.
Changes - July 24th
- fixed massively stupid bug in the jammail.library akalookup function
where previous systems aka variables weren't removed, so if you
connected to a system with a large number of aka's (like mine), and
then called someone with a short number, some of my aka variables would
still be active.
Changes - July 20th
- adjusted timeouts for outbound EMSI sessions - *HOPEFULLY* more reliable
when the remote system has a large banner before their EMSI_REQ line.
Changes - July 13th
- Cleaned some debugging from the AKA lookup function in jammail.library
- removed outbound 256 character EMSI AKA's limitation. Now, up to the
full 2k of AKA's will be sent out. This should also work for outbound
EMSI AKA strings in the custom changes menu as well.
- my AKA defaults should now be cleared when one of your AKA's are loaded
so fields of your AKA that are blank, really are blank, and don't have
my info in it.
Changes - July 11th
- Internal Cnet 3.x launch command updated.
Changes - July 9th
- Timing of of emsi.library improved to handle slower systems that may
not decode a large emsi packet fast enough.
Changes - July 7th
- Poll program now deletes the adaptive dialing stats, so the system will
be polled on the next scheduler scan.
Changes - July 5th
- Collision detection fixed up a bit.
- finished up POLL support with JamTool. POLL now works with all dial
types, and does not attempt to send the 0 byte file (so the filename
is irrelevent now anyways :-)
- cleaned the <got eol> debugging from emsi.library
- fixed up adaptive dialing.
- adjusted timing issues with emsi.library calling systems with large
banners after the EMSI_REQ line.
Changes - July 4th
- Poll program fixed - length of temp name was too long for some PC
systems so would be refused, and the auto-dialing would not stop
- added gpfax options to command line taken from modem stats for
the configured line.
Changes - June 25 - 30
- various fixes in EMSI timeouts
- fixed input routine for AKA's new primary address.
Changes - June 24
- added internal support for GPFax - not *FULLY* tested but should work
for inbound FAX calls. Special thanks to Donald Knott.
- AKA lookup bug in jammail.library fixed where last address listed would
be dropped
Changes - June 22
- working a bit on POLL.
- fixed "bug" in jamtool scheduler that caused creation of alot of
files in env:jamtool/ that were not necessary.
- stack lowered for each line.
- jammail.library only does display in line window.
Changes - June 21
- Completely new POLL program added. Should work with all versions of
JamMail. Requires the scheduler to operate, and when adaptive dial is
disabled, is similar to a regular auto-dial.
Currently, this command should only be used with fidonet type dials
because the polling may never stop with other types, but this will
be fixed in a future version.
Changes - June 20
- Added Adaptive Dial switch for scheduler. Disable this, and the scheduler
will not "dial less often" if busy signals or no-carriers are received.
- jammail.library now has AKA lookup function for EMSI.
- new JamTool is compiled - only has scheduler options. Only a single
binary now.
Changes - June 19
- fixed massively stupid bug relating to the multi-line function of the
scheduler linking in with jammail.library for line set selection.
- fixed bug in the jammail.library lookup function. If you attempted to
dial a non-fidonet site that didn't exist in your phonebook, it would
assume the first fidonet system listed in your nodelist (1:1/0)
and attempt to dial it.
changes - June 17
- modem init string lengthened to 100 from 60.
Changes - June 16
- Added Lookup function to library and JamMail is now using it.
- the system is much smoother now.
- Nullmodem.device is now "temporarily" required for the scheduler.
Unit 8 of nullmodem.device is being used.
- when the new scheduler is done, this will not be required anymore.
Changes - June 15
- Now using jammail.library in JamMail.WPL script. "Duration" already
moved over, now doing Type, wazoo cap, and isvalid.
- timeouts in EMSI.library adjusted to hopefully give more reliable
extreamly high speed connects (ISDN and such).
- added ability to set custom AKA's string for *OUTBOUND* EMSI sessions
- added two more possible lines of each type of address in an EMSI
session (valid, unknown, and invalid).
- cleaned up visual display in emsi/aka's setup menus.
Changes - June 14
- All JamTool functions are now present in JamMail.library other than
the lookup and scheduler functions. A special version of JamTool will
be compiled that only has these functions.
- Brand new Type function added in JamMail.library. This has full stop,
paginate and continuous modes.
- EMSI AKA's string limit raised from 512 to 2048 - allows aprox 100 AKA's
Changes - June 7 -> June 11
- MOOCHO changes to JamTool - still not working, so i'm going to completely
scrap JamTool, and finally, get around to writing the JamMail function
library. This library will hopefully be smaller, and definately faster
since it will not need any ENV: variables. NO MORE CPU SUCKING from the
scheduler.
Changes - June 6
- gone back to JamTool 0.28 because of crashing problems.
- POLL program removed because of this fact.
- this will be fixed and re-distributed.
Changes - June 1
- Archive name shortened to allow PC systems to file request versions,
and for easier distribution on file networks.
Changes - May 30
- Added "POLL" program. It requires the new JamTool to operate.
it adds sites to an automatic poll list, that will be called
everytime the scheduler does a scan. I'll be adding an "UnPoll"
option to it as well.
- this is purely temporary until the new scheduler is written up,
as the new scheduler will have all of this stuff handled better.
- Gone back to previous version of Xferq.library. The one I had compiled
didn't work for some reason. It was likely the cause for the crashing
some people had reported.
Changes - May 28
- JamScan fixed up for NORM handling of FLO and OUT type files
- JamTool massivly cleaned up for CPU usage of Scheduler
- JTPhone bug fixed - showed up when creating new phone list
- "help" command added to Freq/Grab login menu.
Changes - May 24
- More EMSI.library mangling
- almost full plans for new scheduler done on paper.
Changes - May 21
- Cleaning up inbound EMSI handling from other wplemsi.library versions
- starting complete design of new scheduler.
CHANGES - may 19
- ARGGGAGASDFASDFASDFASDF STUPID EMSI BUG!
- new EMSI library finally fixed. Things should be fine now/again.
Changes - May 12
- Wrote a completely new string editing function. Now uses a proper
ADos 2.0 String Gadget for all string inputs.
- still problems with the new emsi.library. don't know why.
Changes - (somewhere in here)
- added timestamp support to emsi.library
Changes - May 1
- *COMPLETELY NEW* emsi handling. JamMail itself modified to be
cleaner, and most of wplemsi.library has been re-written.
Currently full debugging is being shown in the slave window to
attempt to find any further problems.
It seems to work with pretty much every EMSI system i've attempted
to connect to, but it has some problems calling some specific non-EMSI
systems.
Changes - April 27
- Fixed bug that happened "strangly" where inbound Wazoo sessions
weren't possible when the last inbound session was a buggy EMSI
one.
- Generated new Jammail1-preview. Should open on more systems screens.
- will update its menus to include new JamMail options soon.
Changes - April 22 - 26
- forgot to log things - tiny bugs here/there
- CLEANING UP inbound and outbound EMSI.
- adding to JamMail.FAQ
- background work done on JamMail flo monitor (not included yet)
- JamScan "NORM" bug worked on.
Changes - April 21
- Added JamMail.FAQ
- DirectZAP no longer supported in JamMail/EMSI sessions. XprZedZap
0.55 now included in archive. This library is much safer, and
should stop the aborted Zmodem/ZedZip sessions.
Changes - April 19
- Fixing limitations on number of "LOCAL" AKA's for EMSI sessions.
- fixing up more bbslaunch problems
Changes - April 18
- added more commandline logging messages
- added DELETEFLO option to JamScan.
- Fixed BBSLaunch execute string editing problem.
Changes - April 17
- delay in turnaround should fix hanging problem.
- added more commandline logging messages
Changes - April 16
- You can now delete all modems if you wish. You can not exit the Line
configuration menu unless at least one modem is configured though.
- Docs updated with Information about launching Xenolink BBS.
- PhoneLog now uses "Called" address, instead of remote systems primary
address.
Changes - April 15
- Added configuration option for Long Distance phone log filename
- Added options to disable/enable the LDphone log, as well as a new
option to possibly display the log in a window as well.
- Fixing up more commandlines to be logged.
- Fixed Display of Scheduler Log Window size
Changes - April 14
- Having problems with JamScan again. Weird memory things showing up.
- fixing up logging options so command lines are displayed in more sections
when enabled.
Changes - April 9
- Cleaning up DOCUMENTATION! Ya, that DOCUMENTATION STUFF!
- cleaning up wierd display issues found while documenting.
- finally added option to disable inbound processing option of XferqSH.
- adding option to configure "Text:" default for login menu display
files.
Changes - april 7
- cleaning up hangup code for NRC call types
- cleaning up bang hangup code
- cleaning up JamTool
- New JTPhonebook Editor
Changes - April 6
- finally put OS checking code at the beginning of JamMail.
- JamMail1-preview should *HOPEFULLY* give a bit of an error message if it
can't startup for some reason.
Changes - April 5
- various little tidbits fixed/changed
- JamScan 0.60 now included - added MOVE option.
- fixed JamScan MOVE bug (required / at end of path)
Changes - March 29
- little moree twiddling with wplemsi.library - gotta get more reliable
outbound EMSI connects when the banner is missed.
- cleaning JamTool a bit.
Changes - March 19 - 26, 1994
- fiddling with JamTool a bit more, cleaning things up
- JamMail now displays/uses 4 variables from the EMSI AKA string, so this
is about 40 known addresses, 40 unknown addresses, and 40 bad addresses.
- Preliminary work done for JamScan to read .FLO files. Let me know if
any problems arise.
Changes - March 18, 1994
- more changes to JamTool - faster still! smoother scheduler operation
and faster single address lookups.
Changes - March 17, 1994
- Oops, bad wplemsi.library went out.. shit its fixed now.
(gotta love it when people request things *WHILE* they're being
worked on :-)
Changes - March 16, 1994
- Official bugreport.txt added. Please use this when mailing me
bug reports.
- New JamTool included. This one is *MUCH* faster with the AKA lookups
than previous versions.
- New JamScan included. I think i've found the problem with the random
GURU's with JamScan on some systems.. This is .58. It supports
patterns on the destination addresses. I'd like a few systems to
report back to me on how well it works before I fully update the
documentation for it.
To use the routing, do something like this:
route (1|2|3|4|5|6).#?.#?.#? Fidonet#*:*/*.* lzh crash
route (39|40|41).#?.#?.#? AmigaNet#*:*/*.* lha crash
This type of setup, would route addressed with the mentioned zones
to their correct domain.
any systems you want done differently (than LHA/Crash) then you need to
list them beforehand.
- more work on xpremsi.library. Should work better.
Changes - March 12, 1994
- outbound EMSI should always work now.
- minor tweeks here and there.
Changes - March 7, 1994
- little more tweeking with wplemsi.library.
- version string changed for the welcome banner.
Changes - March 6, 1994
- New JamMail1-preview program. Massive changes to most list-views,
and the scheduler screens have actually been done.
- Adding Ymodem as an additional available protocol. This is usefull
for systems that may have flow-control problems. It is positioned
between Zmodem and ZedZap. If someone is having flow control
problems, they should disable DirectZap and ZedZap. Ymodem will be
the highest priority EMSI protocol, so mail from other systems
supporting Ymodem will hopefully be more reliable. Zmodem/ZedZip should
still be left on as other systems will be using it.
The XprYmodem.library file is included if you don't have it. If you
are low on space or ram, simply disable the protocol and delete the
file. This protocol is simply a little extra that some systems may
find handy.
- The "Write Setup" menu option, lists the librarys that JamMail uses
or doesn't use, and it will tell you if your inbound or outbound
directory does not exist.
- New WPL.Library included in the archive. This one has no debugging
in it at all. Along with a clean compiled wplemsi.library, things
should be debugging free.
- Massive work on the JamMail1 gui and new JTPhone gui. Hopefully i'll
have a new JTPhone out soon.
Changes - February 26
- Added launch code for MEBBSNet BBS.
- Added configurable switch to make JamMail ignore possible error
codes from the BBS making JamMail hangup irrelevent of some error
happening.
- Fixed readconfig code, that wasn't allowing multiple BBS Launch
commands.
Changes - Feb 25
- AHHAHAHARGHRGHG I screwed up. The last two archives (the 25th, and
the 18th) likely still had all of the EMSI debugging turned on. So
if you were using the internal serial port and weren't running SUSHI
you'd have no prayor trying to get an EMSI session.
Changes - February 24
- Not much happening in the way of this JamMail. I'm trying to get
a bit going with the new Preview version. The Preview binary
in here is the same as the Feb 18th version.
- There has been some reported problems with the new JamScan56
binary on some machines, with it causing a GURU. IF this does
happen, go back to version 55 (the jamscan055.lha archive is
available on my system, and many others).
- I've done a *LOT* of work on the JamMail1-preview manual. this
one won't go out until JamMail1 itself does since the description
of the software, is relative to the new GUI version of the
software, and some options are in different locations.
- Possibly fixed UUCP/UUCP2 sessions to use any and all versions of
UUCICO, by adding the -Getty switch on outbound calls as well. As
far as I know, they all worked fine for inbound calls, but should
work for outbound as well now.
Changes - February 18
- Gotta love it when I forget to update the .readme :-)
- tweeks and changes in various areas of the system. I can't
remember what all I changed.
- JamScan now allows upto 200 config lines. Previously it was
50 and I just hit that myself :-)
- JamTool has been updated to use a much faster method to do the
EMSI AKA lookups. A new JamTool archive has been sent out
as well.
- All of the AKA/Remote Changes menu options are valid for outbound EMSI
sessions as well (ie, directories, system names), and EMSI itself
can now be disabled (previously it could not be disabled).
- you can now set an option to abort on a CTRL-C in one of the
modem windows. You need to press ctrl-c twice for it to work
however. I'm going to see if I can do anything about this.
Changes - February 6
- Missing Label Error for Fax sessions fixed (DoDial4.4)
Changes - Feburary 2 - 5
- Lots of cleaning up of wplemsi.library.
- EMSI_REQ banner for receiving calls is now hidden to human callers.
(<cr> sent with no linefeed).
- other tweeks with the jammail.wpl file.
- two digit "hex" Product ID is sent in EMSI banner, although since
WPL is 07, it didn't make much difference :-)
Changes - February 1
- Fixed up wplemsi.library. I wasn't verifying the EMSI CRC's because
of a UBYTE problem that I had fixed, but hadn't enabled the CRC
checking again.
Changes - January 31
- There's been a few strange hangups during XprZedZap file transfers.
There is a possibility this is related to Yves's version of the
library. If this problem continues, I am going back to Russ's
version of the library that does not support DirectZap. You will
be able to pickup Yves' library seperately if you wish, but I will
not be including the library capable of DirectZap unless the bug
is found.
Changes - January 30
- *SHIT* right after making up the archive, I found a bug I introduced
yesterday in the wplemsi.library. The host.sitename was not being
sent. No major problem, people just didn't know what the system name
was that was calling them :-)
Changes - January 28
- Cleaning up for an update to the 1210 and 1216 and archives.
- changed name of xpremsi.library to wplemsi.library (since no other
xpr host can use the library right now).
- removed my getline2 function (for string editing) since it was
causing problems, and the new GUI version of JamMail won't be using
any of this stuff anyways.
For people that need to edit some of the really long strings like
possibly your EMSI AKA string, use a regular text editor to edit
the s:Jammail.cfg file, but be carefull not to change anything
else. When you run JamMail to read in that file (and to generate
the mailer), make sure that string was read in correctly).
Changes - January 24
- Fixing up Collision detection with replycall and forward call stuff.
Changes - January 23 - 18
- Various fixing up relating to EMSI
- Inbound EMSI was "finished" sometime in here.
Changes - January 17
- Fixed few minor bugs relating to not having any AKA's or MenuFiles
configured (it was defaulting at having something).
- Finished LogWindow menu.
Changes - January 16
- Window editing displays are fixed up a bit (displays size and upper
left corner instead of raw:x/y/x1/y2 format).
- asynchronously launching bbs's :-)
- Completely re-vamped input routine. Insertion and cursor keys (left/
right) now work.
Changes - January 15
- The version number is now automatically being updated (i'm lazy:-)
- Added NoDrag/NoSize and BackDrop options to LogWindows menu. *ALL*
windows will have these options (except xpr transfer windows will
not have backdrop option);
- Now generating S:Setup batch file. Logfile and LogWindow are now
configurable and written in this file. The LDPhoneLog is also
configurable and written in the setup script.
Changes - January 14
- Added Modem Banging config. 3 choices. Soft, Medium and Hard.
This selects which string will be sent to the modem after every session
to get control of the modem back (ie, until an OK response is received).
NullModem.Device does not support the Hard banging type.
The Soft is basically an AT, the Medium is an ATZ and the Hard is an AT&F.
If you previously had the Medium or Hard in your Init string, you don't
need it any long if you use it here.
- All protocol selection code is generated only if needed. If you don't
want ZedZap used, no inbound or outbound zedzap code is written to
the .wpl file.
- Init and Attention modem strings lengthened to 60 characters.
Changes - January 13
- Added DirectZap support for outbound EMSI sessions. (I think !? :-)
- Cleaning up inbound Fidonet sessions now. WaZoo and EMSI protocol
selection is now done the same way as the way i'm doing it for outbound
protocols. Now all we need, is Inbound EMSI support.
Changes - January 12th, 94
- more internal cleaning
Changes - January 11th
- My USHayes V.FC 28.8k modem arrived. I'm going to change the (TIME)
response type to a simple (LOG) response, so anything that has this
response type will simply be logged. Nothing else special is done
with anything that matches. Also, the response type (LOG) will not
be put on the end of the line (like RING and others is done).
- All outbound Fidonet session code re-done. It is now easy to add
new protocols to WaZoo or EMSI sessions.
- Protocols available are now configurable in Fidonet -> Other menu.
- Re-write of alot of the outbound dialing sequence. Collision detection
is now much better (theoretically!).
- Additional internal ModemInit added to mailer. Cleans up alot of
possible junk that could happen before main INIT was done after a
dial/session.
Changes - January 10th
- Still cleaning internals & sources
Changes - January 9th
- Massive cleanup of internal JamMail code.
- You can now only select Handshaking methods for your Aka's that are
turned on by default.
Changes - January 8th
- Added UUCP2 session type. You may want to have two different sets
of UUCICO options, one for regular systems, and one for systems that
can handle larger block sizes and faster sessions.
JTPhone will be updated to handle this as well.
- I think inbound FAX reception has been fixed. Thanks to Todd Vierling
for the code.
Changes - January 6th
- The AddModem fuction should actuall add the correct defaults for the
modem you select.
- Actually fixed the defaults for Nullmodem.device lines.
- Included the CNet BBS launch string as default #3. Since it is only
a single command line, the command line is actually placed in the
launch string so you can see it (the DLG and VBBS launch commands are
more than one line, so are just generated in your mailer).
Changes - January 5th
- Oops, I haven't been making my entries!
- Full outbound EMSI is now being done (actually, it was done before my
Xmas vacation, but I didn't mention it here :-)
- Scheduler timeouts now have a maximum of 9999 seconds instead of 255.
- Init timeout value is now configurable for each line (wasn't configurable
at all previously).
- Pre-fido bug reported in wpl-programmer fixed.
- inbound and outbound directory prompts actually add '/' character if
not already there.
--------
Happy New year guys!
Changes - December 15
- Back to EMSI work. Now actually attempting to do WPL variable handling
from inside XprEMSI.library.
- latest Wpl.Library included in archive now. - Fixes RexxMsg bug.
Changes - December 8
- Completely cleaned random "OK" messages popping up in log messages that
come back from modems that take a long time to init (ie, slow 2400 with
an AT&F in the init string).
Changes - December 5
- Still playing with EMSI (not included in this archive)
- New security option added to JamTool/JamMail. This makes sure people
aren't using the nice escape sequences possible in the execute commands
in either the main login menu, or the freq server name input routine.
Changes - December 3
- Due to the Mad hacker - i've cleaned up a few input routines that
could have been used to do nasty things.
Changes - December 1
- Fixed timeout in ModemInit routine that was causing "OK" results
to show up in the main log window with extreamly slow modems (slow
at resetting if you did an ATZ as your init/atten string).
- Setting the current modem to 300bps before dialing NRC systems for
better compatibility with different modems attempting to do the
connection.
Changes - November 22-25
- Working on outbound EMSI support. This stuff will not be included in
the current archive, but this is to let you know what i'm working
on. Inbound EMSI will be added after outbound is done.
Changes - November 21
- problem with "-ListConfig" command was causing a guru after
startup of JamMail. The command has been removed since it was only
being used for debugging purposes anyways.
Changes - November 19
- Now including JamScan and JamTool in the JamMail archive along
with their respective documentation files.
Changes - November 18
- Lots of work done on the Documentation. Completed the FidoNet
configs area (updated to the new menu set), and added the Login
Menu section.
- archive is now named in the "JamMailDDMM.Lha" style, with the
day and month.
Changes - November 17
- Re-structuring menu system - Fidonet options are cleaned up, the
documentation will be a little wrong during this time. The Privacy
modes are now a single option in the "Login Menu" that selects each
of the options in order. Cleaning up the code that uses these
settings as well.
- The inbound and outbound directory selections were moved to the
Fidonet configs menu.
- privacy variables removed, more cleaning up.
Changes - November 16
- Call script included. You can set the Execute bit on this script
or have an alias that executes it. This command will take a single
parameter (an address, or portion of a FTN address) and it will
add that system to the scheduler dial list.
- Due to this change with the scheduler, when call collisions occur,
calls are forwarded back to the scheduler in hopes that the call
being attempted can be sent to another line (if this is a multi-line
system).
- Finally updated TODO: list. Most of it had been done!
Changes - November 15
- Scheduler slave (message port "JAMMAIL") now accepts call commands.
After it scans for systems in Xferq (and UUSPOOL: if configured to
do so), it will check to see if a call command has been sent to it.
If a call has been received, that system is added to the top of the
ToDial list, and it will be dialed first. Only one call command
per scan will be added. It is recommended that you use an alias
like:
Alias Call run <nil: >nil: rx "Address 'JAMMAIL' 'Call []'"
to do manual dials.
If you wish the call to be done immediately (assuming it is in a
waitloop), send a Ctrl-F (Timeout) to the slave right after you
send the Dial. (You could have the CALL Alias execute a script
that does both).
Changes - November 10
- The scheduler accounting system now does not operate on "TERM" type
dials, so it does not dial less often to these systems if they are
busy.
- One Note: currently, UUCP dials (systems looked up in the UUSPOOL:
directory, don't use this system either). Anything that uses Xferq
(other than TERM types) does.
Changes - November 7
- Fixed a couple windows up. The introduction of Public Screens wasn't
completely finished :-)
Changes - November 4
- Bug fix - the system wasn't allowing the situation where the user
didn't have any AKA's configured. It defaulted to having one,
which caused problems with the written script.
******************************************************
- Changes from March to October 93 Deleted -
******************************************************
Note: You *MUST* be running SUSHI or have a terminal connected to your internal
serial port to use the current debugging versions of wpl.library and xferq.library.
Unless otherwise stated, you will be running debug versions of the librarys if you
got them with this archive.
-----------------------------------------------------------------------
TODO:
- Dmodem support.
- Temporary new Scheduler - calling time zones defined. First version
without JamTool binary included at all.
Line scan orders for different "call time zones".
- Direct support for TrapDoor style Freq handler command lines - new
XferqSH type program.
- small QuickFreq server (part of new XfreqSH program)
- single binary replacing setup script, and the loadscript and launch
programs. Possibly add creation of own public screen at this point.
- Direct accepting of TD style BBS launch commands (converts variables
from TD style % variables to $() variables). Is this even relevent?
- completely new schedler - graphical, with scroll bar of systems with
mail and the priority. Bar will move on top of system address being
polled.
- Full AmigaGuide format Documentation.
- Auto-window location generator (calculates "good looking" locations for
log/session/scheduler windows/etc.). Possibly even re-writes s:jammail.cfg
file with new values. Or maybe it will be a module of "JAMMAIL" itself
and part of the main configuration.
- Audio inbound/outbound file/session announcement option (configurable
messages).
- AmiTCP sessions - as much support as is required/requested for
full "SLIP/PPP FTP/TelNet" session types.